Mechanism for facilitating user-controlled management of site network mapping and synchronization

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for facilitating user-controlled mapping of sites and synchronization of their content. In one embodiment and by way of example, a method includes receiving a first generation request for generating a site template in a first site network. The first generation request is received at a first computing device. The method may further include generating the site template, generating a child site based on the site template, and mapping the child site to one or more of a parent site and one or more child sites within the first site network.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional Patent Application No. 61/621,665, entitled “Site Networks and Cross-Site Sharing” by Philip Normal Calvin, et al., filed Apr. 17, 2012 (Attorney Docket No.: 8956P097Z), the entire contents of which are incorporated herein by reference and priority is claimed thereof.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

TECHNICAL FIELD

One or more implementations relate generally to data management and, more specifically, to a mechanism for facilitating user-controlled management of site network mapping and synchronization.

BACKGROUND

In the growing world of computing technology, various techniques exist for mapping of websites within a network, but these conventional techniques and not user-controlled as they require high programming skills. Thus, such conventional mapping techniques are typically performed by computer programmers, system administrators, etc., that possess high level of programming skills that are above and beyond the skills of a typical end-user.

The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches.

In conventional database systems, users access their data resources in one logical database. A user of such a conventional system typically retrieves data from and stores data on the system using the user's own systems. A user system might remotely access one of a plurality of server systems that might in turn access the database system. Data retrieval from the system might include the issuance of a query from the user system to the database system. The database system might process the request for information received in the query and send to the user system information relevant to the request. The secure and efficient retrieval of accurate information and subsequent delivery of this information to the user system has been and continues to be a goal of administrators of database systems. Unfortunately, conventional database approaches are associated with various limitations.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples, one or more implementations are not limited to the examples depicted in the figures.

FIG. 1 illustrates a computing device employing a mechanism for facilitating user-controlled management of site network mapping and synchronization according to one embodiment;

FIG. 2 illustrates a mechanism for facilitating user-controlled management of site network mapping and synchronization according to one embodiment;

FIG. 3A illustrates a user-controlled management of site network using a mechanism for facilitating user-controlled management of site network mapping and synchronization of FIG. 1 according to one embodiment;

FIG. 3B illustrates a user-controlled management of site network using a mechanism for facilitating user-controlled management of site network mapping and synchronization of FIG. 1 according to one embodiment;

FIG. 4 illustrates a method for facilitating user-controlled management of site network mapping and synchronization according to one embodiment;

FIG. 5 illustrates a computer system according to one embodiment;

FIG. 6 illustrates a block diagram of an environment wherein an on-demand database service might be used according to one embodiment; and

FIG. 7 illustrates a block diagram of an embodiment of elements of environment of FIG. 6 and various possible interconnections between these elements according to one embodiment.

DETAILED DESCRIPTION

Methods and systems are provided for facilitating user-controlled mapping of sites and synchronization of their content. In one embodiment and by way of example, a method includes receiving a first generation request for generating a site template in a first site network. The first generation request is received at a first computing device. The method may further include generating the site template, generating a child site based on the site template, and mapping the child site to one or more of a parent site and one or more child sites within the first site network.

In one embodiment, a mechanism for facilitating user-controlled management of site network mapping and synchronization is provided to allow a user (e.g., owner (e.g., a company, an organization, etc.) of a parent site, a customer of the owner, etc.) to control how the data is synched and presented on the parent site and any number of child sites, such as to push any changes from the parent site to one or more child sites work-in-progress as well as have an ability to update the child sites live version and further, to allow the user to make changes to the site-network structure as desired or necessitated.

As used herein, a term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. As used herein, the term query plan refers to a set of steps used to access information in a database system.

Embodiments are described with reference to an embodiment in which techniques for facilitating management of data in an on-demand services environment are implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, embodiments are not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.

Next, mechanisms and methods for facilitating user-controlled mapping of sites and synchronization of their content will be described with reference to example embodiments.

FIG. 1 illustrates a computing device 100 employing a mechanism for facilitating user-controlled management of site network mapping and synchronization (“mapping and synchronization mechanism”) 110 according to one embodiment. In one embodiment, computing device 100 serves as a host machine employing dynamic customization mechanism 110 for providing dynamic customization of information by facilitating user-based control of management of mapping of websites and synchronization of their content within a network and/or over multiple networks as will be described further in this document.

Computing device 100 may include server computers (e.g., cloud server computers, etc.), desktop computers, cluster-based computers, set-top boxes (e.g., Internet-based cable television set-top boxes, etc.), and the like. Computing device 100 may also include smaller computers, such as mobile computing devices, such as cellular phones including smartphones (e.g., iPhone® by Apple®, BlackBerry® by Research in Motion®, etc.), handheld computing devices, personal digital assistants (PDAs), etc., tablet computers (e.g., iPad® by Apple®, Galaxy® by Samsung®, etc.), laptop computers (e.g., notebooks, netbooks, Ultrabook™, etc.), e-readers (e.g., Kindle® by Amazon.com®, Nook® by Barnes and Nobles®, etc.), Global Positioning System (GPS)-based navigation systems, etc.

Computing device 100 includes an operating system (OS) 106 serving as an interface between any hardware or physical resources of the computing device 100 and a user. Computing device 100 further includes one or more processors 102, memory devices 104, network devices, drivers, or the like, as well as input/output (I/O) sources 108, such as touchscreens, touch panels, touch pads, virtual or regular keyboards, virtual or regular mice, etc. It is to be noted that terms like “node”, “computing node”, “client”, “client device”, “server”, “server device”, “cloud computer”, “cloud server”, “cloud server computer”, “machine”, “host machine”, “device”, “computing device”, “computer”, “computing system”, “multi-tenant on-demand data system”, and the like, may be used interchangeably throughout this document. It is to be further noted that terms like “application”, “software application”, “program”, “software program”, “package”, and “software package” may be used interchangeably throughout this document.

FIG. 2 illustrates a mechanism for facilitating user-controlled management of site network mapping and synchronization 110 according to one embodiment. In one embodiment, using mapping and synchronization mechanism 110 provides various tools and techniques to further modernize cross-site sharing concepts of Salesforce.com® by, for example, allowing user-control of site mapping and content synchronization. Example of user 235 includes an owner of a parent site, where the owner may include an organizational customer (such as a small or large business, a company, a corporation, an academic institution, a government agency, a non-profit organization, etc.) of a service provider (e.g., Salesforce.com) and/or an individual customer, such as individuals or end-users, of the organization customers that may be given the same may be given a parent site and extended the same management privileges by the owner or the organizational customer. It is to be noted that terms like “user”, “customer”, “organization”, “business”, “company”, etc., may be used interchangeably throughout this document.

In one embodiment, mapping and synchronization mechanism 110 may be employed at a server computing system, such as computing device 100 of FIG. 1, may be in communication with any number and type of computing devices serving as client computing devices, such as computing device 220 employing a client-based application 222 having a user interface 224 providing user access to user 226 (e.g., a representative of an organization that is an owner of a parent site provided by a service provider (such as Salesforce.com) that further provides user-controlled access to and management of site network mapping and synchronization via mapping and synchronization mechanism 110) over a network 230 (such as the Internet, a cloud computing network, etc.). Similarly, it is contemplated that a user may include other users, such as an individual or a small business 245, etc., that is a customer of an organization/organizational customer that is represented here by user 226. Client computing devices 220 may be the same as or similar to computing device 100 of FIG. 1 and include smaller computers, such as a mobile computing device (e.g., smartphones, tablet computers, etc.) or larger computers (such as a desktop computer, a server computer, etc.).

In the illustrated embodiment, mapping and synchronization mechanism 110 includes various components, such as authentication logic 202, request reception logic 204 (having analysis module 205), creation logic 206, selection logic 208, mapping logic 210, synchronization logic 212 (having copying/deployment module 214, overwriting module 216, error resolution module 218), database/depot access logic 220, and compatibility logic 222. Throughout this document, the term “logic” may be interchangeably referred to as “component” or “module” and may include, by way of example, software, hardware, and/or any combination of software and hardware, such as firmware. This combination of components 202-222 provides user-based mapping of sites and synchronization of contents of those sites without having to require any computer/technical or Internet programming qualifications or skills on the user-end (in contrast to the conventional systems that require a user to be a skilled computer programmer and the user's organization to have sophisticated equipment).

In one embodiment, authentication logic 202 may be used to authenticate user 226, their organization, and/or their computing device 220 before they are allowed the authority to map or synchronize. It is contemplated that, in some embodiments, the authentication process may be a one-time process conducted when the organization is registered or downloads client-based application 222 on their computing device 220 and/or when computing device 220 is first allowed access mapping and synchronization mechanism 110. In other embodiments, authentication may be a recurring process to be performed each time a task for mapping and/or synchronization is requested (via client-based application 222 and further via user interface 224) and received by request reception logic 204 at mapping and synchronization mechanism 110 employed at the cloud-based server computer over network 230.

In one embodiment, each time a user 226 attempts to perform a mapping or synchronization task, via client-based application 222, the attempt may be received as a request at request reception logic 204 where it is analyzed by analysis module 205 and then appropriately forwarded on for further processing. For example, creating site-template definitions from a site and then creating child sites using the site-template definitions may be performed by creation logic 206. Similarly, selection logic 208 may be used to select one or more child sites to be mapped to the parent site using mapping logic 210.

Once the mapping is performed, any number and type of changes may be made to the parent site and/or one or more mapped child sites, such as new content may be added to or deletions or updates, etc., may be made to existing contents of relevant parent and child sites. Further, new sites may be added having new content, such as, using creating logic 206, new templates may be created and then, new sites may be created using the new templates with new content which may then be synchronized with the parent site and other child sites using synchronization logic 212. In some embodiments, mapping and/or synchronization may be performed between various sites within a site network; while, in other embodiments, mapping and/or synchronization may be performed between sites of multiple sites networks.

In one embodiment, any amount of content or any changes to the content of one site may be copied to (including by pushing or pulling) or deployed at other sites using copying/deployment module 214. Similarly, content of a site may be wholly overwritten with, for example, contents of another site using overwriting module 216. If there are any errors detected in the content of any of the sites, they may be resolved or corrected using error resolution module 218. Further, in one embodiment, depot 225 may serve as a database or repository of relevant information (e.g., asset, content) and depot access logic 220 may facilitate access to depot 225 to access and retrieve any of that information contained at depot 225 to change or update or support the existing content at one or more sites. As illustrated, depot 225 is maintained in communication with the cloud-based server computing device having mapping and synchronization mechanism 110. Compatibility logic 222 allows for mapping and synchronization mechanism 110 to maintain compatibility with any number and types of sites, computing devices 220, networks 230, or the like.

It is contemplated that any number and type of components may be added to and/or removed from mapping and synchronization mechanism 110 to facilitate various embodiments including adding, removing, and/or enhancing certain features. For brevity, clarity, and ease of understanding of mapping and synchronization mechanism 110, many of the standard and/or known components, such as those of a computing device, are not shown or discussed here. It is contemplated that embodiments are not limited to any particular technology, topology, system, architecture, and/or standard and are dynamic enough to adopt and adapt to any future changes.

FIG. 3A illustrates a user-controlled management of site network 300 using mapping and synchronization mechanism 110 of FIG. 1. In one embodiment, using various components 202-222 of mapping and synchronization mechanism 110 and client-based application 222 of FIG. 2, a user, such as user 226 of FIG. 2 and owner of parent site 302, may generate various site templates 304-308 and use them to generate various corresponding child sites 310-318 that are then mapped to parent site 302 and their contents are synchronized. For example, the user or parent site owner may include an organization or company (e.g., BMW®, Minnesota Mining and Manufacturing (3M™), etc.) having business in various parts of world, such as in any number of countries in various continents around the world. Continuing with the example, the user, such as BMW, wishes to have customized sites for their customers in BMW North America (NA), BMW Europe, and BMW Asia. A user representing BMW may generate site templates 304-308, corresponding to BMW NA, BMW Europe, and BMW Asia, that contain information relevant to their customers in those parts of the world, such as site template 304 may correspond to BMW NA, site template 306 to BMW Europe, and site template 308 to BMW Asia. The user may use any number of child sites 310-318 using site templates, where, for example, child sites 310-318 may correspond to specific countries, such as child site 310 may correspond to the United States of America and child site 312 may correspond to Mexico. Both child sites 310, 312 may be generated using site template 304 corresponding to BMW NA.

In one embodiment, specific components may be constructed on child sites 310-318 and are used to specify default parameters (even locking these parameters), such as a new product page to the product page, a new biographic page which may be added to “About Us” page, etc., that are specific to each child site 310-312. Similarly, various components may be defined and assigned specific to particular one or more site templates 304-308 which may then be synchronized with one or more of their corresponding child sites 310-312 and/or to parent site 302. Similarly, changes or updates may be made to parent site 302 and then be synchronized by deploying or copying down to one or more child sites 310-318 via one or more site templates 304-308. These updates may be performed using various copy/deploy/share techniques, such as a push technique, a pull technique, etc., to synchronize the relevant content between various sites 302, 310-318 and site templates 304-308. Further, relevant content may be pulled from or stored at depot 225 having asset library, content library, etc.

In the illustrated embodiment of FIG. 3A, parent site 302 (or depot site for being in communication with depot 225) may copy its contents (including changes/updates) into its connected child sites 310-318 either directly (as illustrated in FIG. 3B) or via one or more intermediate child sites or further via one or more template sites 304-308. Contents or changes/updates, including pages, templates, stylesheets, content type, content items, assets, etc., may be synchronized and shared between even a work-in-progress version of parent site 302 and a work-in-progress area of child sites 310-318 and may be stored at or shared with content at depot 225. Further, each child site 310-318 may have an owner that may be separate from (but be a subsidiary of) the owner of parent site 302 and thus, each child site owner may have a separate and independent authority to make changes to child sites 310-318 which may then be pushed up to parent site 302 and/or depot 225.

In case of any errors or discrepancies, such as due to invalid components (e.g., broken references or links, a parent object that no longer exists or is detached so it have become orphaned, etc.), discrepancy in content types (such as content type (e.g., schema) is changed at parent site 302, the existing content items at one or more child sites 310-318 that are incompatible with the content type at parent site 302 are to be resolved (such as by adding or removing fields, etc.), or the like, using error resolution logic 218 of mapping and synchronization mechanism 110 as illustrated in FIG. 2. Further, for example, error resolution logic 218 may facilitate swapping of one or more site templates 304-308 with each other or with any of site templates 304-308 having added, changed and/or removed components and/or contents.

In some embodiments, re-parenting of sites 302, 310-318 may be performed and their content by re-synchronized to serve a particular customer pool, such as a country, a set of countries, a continent, a region based on culture, purchasing power, etc. For example, the user may move child site 316, 318 away from parent site 302 to another parent site. Further, for example, the user/BMW may choose to dedicate child site 316 to the Middle Eastern region of Asia. Similarly, for example, the user/BMW may choose to re-classify the other child site 318 as a new parent site dedicated to the rest of Asia and for additional customized services, the user may create and deploy one or more new child sites under the newly-classified parent site (previously child site) 318 to serve one or more other regions of Asia, such as South Asia, Central Asia, South-East Asia, etc. The new parent site may be placed in communication with and provided access to depot 225 or another depot associated with site network 300. In some embodiment, sites 302, 310-318 may be mapped to and their contents synchronized with other parent sites and/or child sites in other site networks.

FIG. 3B illustrates a user-controlled management of site network 350 using mapping and synchronization mechanism 110 of FIG. 1. For brevity and clarity, various components and their functions previously discussed with reference to FIGS. 1, 2 and 3A are not discussed here. In the illustrated embodiment, root template site 352 is parent template to template site 354. As illustrated, child sites 360-364 are created and based directly from root template site 352, while child sites 356, 358 are created from and based on template site 354. Further, root template site 352 is shown in communication with and having access to depot 225.

FIG. 4 illustrates a method 400 for facilitating user-controlled management of site network mapping and synchronization according to one embodiment. Method 400 may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (such as instructions run on a processing device), or a combination thereof. In one embodiment, method 400 may be performed by mapping and synchronization mechanism 110 of FIG. 1.

Method 400 begins with block 405 where a site template is generated based on a request received, at a server computing device, from a user via a client computing device over a network. The received request may be authenticated prior to being analyzed for its contents. At block 410, the request is analyzed and, accordingly, forward on for processing. At block 415, a child site is generated based on the site template. It is contemplated that the site template may be used to generate another parent site and/or any number of child sites. At block 420, the child site is mapped to a parent site and/or one or more child sites. At block 425, contents of the newly-created child site are synchronized with contents of the mapped parent site and/or one or more child sites and vice versa. As aforementioned, synchronization of contents may include any number and type of processes, such as adding, deleting, copying, deploying, pushing, pulling, sharing, overwriting, error resolution/correction, etc. It is contemplated and as discussed above, various other processes such as re-classification of sites, templates, accessing of depot, etc., may also be performed, as desired or necessitated, at various stages of any of the aforementioned processes.

FIG. 5 illustrates a diagrammatic representation of a machine 500 in the exemplary form of a computer system, in accordance with one embodiment, within which a set of instructions, for causing the machine 500 to perform any one or more of the methodologies discussed herein, may be executed. Machine 500 is the same as or similar to computing device 100 and computing devices 230, 240 of FIG. 1 and FIG. 2, respectively. In alternative embodiments, the machine may be connected (e.g., networked) to other machines in a network (such as machine 110 of FIG. 1 connected with machines 230, 240 of FIG. 2 over network 250), such as a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet. The machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment or as a server or series of servers within an on-demand service environment, including an on-demand environment providing multi-tenant database storage services. Certain embodiments of the machine may be in the form of a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, computing system, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The exemplary computer system 500 includes a processor 502, a main memory 504 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc., static memory such as flash memory, static random access memory (SRAM), volatile but high-data rate RAM, etc.), and a secondary memory 518 (e.g., a persistent storage device including hard disk drives and persistent multi-tenant data base implementations), which communicate with each other via a bus 530. Main memory 504 includes emitted execution data 524 (e.g., data emitted by a logging framework) and one or more trace preferences 523 which operate in conjunction with processing logic 526 and processor 502 to perform the methodologies discussed herein.

Processor 502 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor 502 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 502 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processor 502 is configured to execute the processing logic 526 for performing the operations and functionality of dynamic customization mechanism 110 as described with reference to FIG. 1 and other figures discussed herein.

The computer system 500 may further include a network interface card 508. The computer system 500 also may include a user interface 510 (such as a video display unit, a liquid crystal display (LCD), or a cathode ray tube (CRT)), an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), and a signal generation device 516 (e.g., an integrated speaker). The computer system 500 may further include peripheral device 536 (e.g., wireless or wired communication devices, memory devices, storage devices, audio processing devices, video processing devices, etc. The computer system 500 may further include a Hardware based API logging framework 534 capable of executing incoming requests for services and emitting execution data responsive to the fulfillment of such incoming requests.

The secondary memory 518 may include a machine-readable storage medium (or more specifically a machine-accessible storage medium) 531 on which is stored one or more sets of instructions (e.g., software 522) embodying any one or more of the methodologies or functions of dynamic customization mechanism 110 as described with reference to FIG. 1 and other figures described herein. The software 522 may also reside, completely or at least partially, within the main memory 504 and/or within the processor 502 during execution thereof by the computer system 500, the main memory 504 and the processor 502 also constituting machine-readable storage media. The software 522 may further be transmitted or received over a network 520 via the network interface card 508. The machine-readable storage medium 531 may include transitory or non-transitory machine-readable storage media.

Portions of various embodiments may be provided as a computer program product, which may include a computer-readable medium having stored thereon computer program instructions, which may be used to program a computer (or other electronic devices) to perform a process according to the embodiments. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disk read-only memory (CD-ROM), and magneto-optical disks, ROM, RAM, erasable programmable read-only memory (EPROM), electrically EPROM (EEPROM), magnet or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.

The techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer-readable media, such as non-transitory computer-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer-readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals). In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device. Of course, one or more parts of an embodiment may be implemented using different combinations of software, firmware, and/or hardware.

FIG. 6 illustrates a block diagram of an environment 610 wherein an on-demand database service might be used. Environment 610 may include user systems 612, network 614, system 616, processor system 617, application platform 618, network interface 620, tenant data storage 622, system data storage 624, program code 626, and process space 628. In other embodiments, environment 610 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.

Environment 610 is an environment in which an on-demand database service exists. User system 612 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 612 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in herein FIG. 6 (and in more detail in FIG. 7) user systems 612 might interact via a network 614 with an on-demand database service, which is system 616.

An on-demand database service, such as system 616, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 616” and “system 616” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 618 may be a framework that allows the applications of system 616 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 616 may include an application platform 618 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 612, or third party application developers accessing the on-demand database service via user systems 612.

The users of user systems 612 may differ in their respective capacities, and the capacity of a particular user system 612 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 612 to interact with system 616, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 616, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.

Network 614 is any network or combination of networks of devices that communicate with one another. For example, network 614 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that one or more implementations might use are not so limited, although TCP/IP is a frequently implemented protocol.

User systems 612 might communicate with system 616 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 612 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 616. Such an HTTP server might be implemented as the sole network interface between system 616 and network 614, but other techniques might be used as well or instead. In some implementations, the interface between system 616 and network 614 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.

In one embodiment, system 616, shown in FIG. 6, implements a web-based customer relationship management (CRM) system. For example, in one embodiment, system 616 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 612 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, system 616 implements applications other than, or in addition to, a CRM application. For example, system 616 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 618, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 616.

One arrangement for elements of system 616 is shown in FIG. 6, including a network interface 620, application platform 618, tenant data storage 622 for tenant data 623, system data storage 624 for system data 625 accessible to system 616 and possibly multiple tenants, program code 626 for implementing various functions of system 616, and a process space 628 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 616 include database indexing processes.

Several elements in the system shown in FIG. 6 include conventional, well-known elements that are explained only briefly here. For example, each user system 612 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. User system 612 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 612 to access, process and view information, pages and applications available to it from system 616 over network 614. Each user system 612 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 616 or other systems or servers. For example, the user interface device can be used to access data and applications hosted by system 616, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 612 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 616 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 617, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring system 616 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 616 is configured to provide webpages, forms, applications, data and media content to user (client) systems 612 to support the access by user systems 612 as tenants of system 616. As such, system 616 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

FIG. 7 also illustrates environment 610. However, in FIG. 7 elements of system 616 and various interconnections in an embodiment are further illustrated. FIG. 7 shows that user system 612 may include processor system 612A, memory system 612B, input system 612C, and output system 612D. FIG. 7 shows network 614 and system 616. FIG. 7 also shows that system 616 may include tenant data storage 622, tenant data 623, system data storage 624, system data 625, User Interface (UI) 730, Application Program Interface (API) 732, PL/SOQL 734, save routines 736, application setup mechanism 738, applications servers 700 ₁-700 _(N), system process space 702, tenant process spaces 704, tenant management process space 710, tenant storage area 712, user storage 714, and application metadata 716. In other embodiments, environment 610 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system 612, network 614, system 616, tenant data storage 622, and system data storage 624 were discussed above in FIG. 6. Regarding user system 612, processor system 612A may be any combination of one or more processors. Memory system 612B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 612C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 612D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 7, system 616 may include a network interface 620 (of FIG. 6) implemented as a set of HTTP application servers 700, an application platform 618, tenant data storage 622, and system data storage 624. Also shown is system process space 702, including individual tenant process spaces 704 and a tenant management process space 710. Each application server 700 may be configured to tenant data storage 622 and the tenant data 623 therein, and system data storage 624 and the system data 625 therein to serve requests of user systems 612. The tenant data 623 might be divided into individual tenant storage areas 712, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage area 712, user storage 714 and application metadata 716 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 714. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area 712. A UI 730 provides a user interface and an API 732 provides an application programmer interface to system 616 resident processes to users and/or developers at user systems 612. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.

Application platform 618 includes an application setup mechanism 738 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 622 by save routines 736 for execution by subscribers as one or more tenant process spaces 704 managed by tenant management process 710 for example. Invocations to such applications may be coded using PL/SOQL 734 that provides a programming language style interface extension to API 732. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Method and System for Allowing Access to Developed Applicants via a Multi-Tenant Database On-Demand Database Service”, issued Jun. 1, 2010 to Craig Weissman, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata 716 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server 700 may be communicably coupled to database systems, e.g., having access to system data 625 and tenant data 623, via a different network connection. For example, one application server 700 ₁ might be coupled via the network 614 (e.g., the Internet), another application server 700 _(N-1) might be coupled via a direct network link, and another application server 700 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 700 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 700 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 700. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 700 and the user systems 612 to distribute requests to the application servers 700. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 700. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 700, and three requests from different users could hit the same application server 700. In this manner, system 616 is multi-tenant, wherein system 616 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 616 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 622). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 616 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data, system 616 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

In certain embodiments, user systems 612 (which may be client systems) communicate with application servers 700 to request and update system-level and tenant-level data from system 616 that may require sending one or more queries to tenant data storage 622 and/or system data storage 624. System 616 (e.g., an application server 700 in system 616) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 624 may generate query plans to access the requested data from the database.

Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain embodiments, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.

Any of the above embodiments may be used alone or together with one another in any combination. Embodiments encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments do not necessarily address any of these deficiencies. In other words, different embodiments may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

While one or more implementations have been described by way of example and in terms of the specific embodiments, it is to be understood that one or more implementations are not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. It is to be understood that the above description is intended to be illustrative, and not restrictive. 

What is claimed is:
 1. A method comprising: receiving a first generation request for generating a site template in a first site network, wherein the first generation request is received at a first computing device; generating the site template; generating a child site based on the site template; and mapping the child site to one or more of a parent site and one or more child sites within the first site network.
 2. The method of claim 1, wherein the request is placed, via a user interface, at a second computing device including a client computing device, the client computing device having desktop computing devices or mobile computing devices, wherein the request is placed by a representative of an organization including one or more of a business, a government agency, an educational institution, a non-profit organization.
 3. The method of claim 2, wherein the request is received at the first computing device over a network, wherein the first computing device includes a server computing device coupled with the second computing device over the network, wherein the network comprises one or more of a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet.
 4. The method of claim 1, further comprising receiving a synchronization request to synchronization first content of the child site with one or more of second content of the parent site and third content of the one or more child sites; and synchronizing first content of the child site with the one or more of the second content of the parent site and the third content of the one or more child sites.
 5. The method of claim 1, further comprising: authenticating the first generation request prior to processing the request; and processing the request prior to generating the site template.
 6. The method of claim 1, further comprising: receiving a second generation request for generating the child site based on the site template; and receiving a mapping request for mapping the child site to the one or more of the parent site and the one or more child sites within the site network.
 7. The method of claim 1, further comprising mapping or synchronizing the child site with one or more sites at a second site network, wherein the one or more sites include one or more of parents sites and child sites at the second site network.
 8. A system comprising: a computing device having a memory to store instructions, and a processing device to execute the instructions, the computing device further having a mechanism to: receive a first generation request for generating a site template in a first site network, wherein the first generation request is received at a first computing device; generate the site template; generate a child site based on the site template; and map the child site to one or more of a parent site and one or more child sites within the first site network.
 9. The system of claim 8, wherein the request is placed, via a user interface, at a second computing device including a client computing device, the client computing device having desktop computing devices or mobile computing devices, wherein the request is placed by a representative of an organization including one or more of a business, a government agency, an educational institution, a non-profit organization.
 10. The system of claim 9, wherein the request is received at the first computing device over a network, wherein the first computing device includes a server computing device coupled with the second computing device over the network, wherein the network comprises one or more of a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet.
 11. The system of claim 8, wherein the mechanism is further to: receive a synchronization request to synchronization first content of the child site with one or more of second content of the parent site and third content of the one or more child sites; and synchronize first content of the child site with the one or more of the second content of the parent site and the third content of the one or more child sites.
 12. The system of claim 8, wherein the mechanism is further to: authenticate the first generation request prior to processing the request; and process the request prior to generating the site template.
 13. The system of claim 8, wherein the mechanism is further to: receive a second generation request for generating the child site based on the site template; and receive a mapping request for mapping the child site to the one or more of the parent site and the one or more child sites within the site network.
 14. The system of claim 8, further comprising mapping or synchronizing the child site with one or more sites at a second site network, wherein the one or more sites include one or more of parents sites and child sites at the second site network.
 15. A machine-readable medium having stored thereon instructions which, when executed by a machine, cause the machine to: receive a first generation request for generating a site template in a first site network, wherein the first generation request is received at a first computing device; generate the site template; generate a child site based on the site template; and map the child site to one or more of a parent site and one or more child sites within the first site network.
 16. The machine-readable medium of claim 15, wherein the request is placed, via a user interface, at a second computing device including a client computing device, the client computing device having desktop computing devices or mobile computing devices, wherein the request is placed by a representative of an organization including one or more of a business, a government agency, an educational institution, a non-profit organization.
 17. The machine-readable medium of claim 16, wherein the request is received at the first computing device over a network, wherein the first computing device includes a server computing device coupled with the second computing device over the network, wherein the network comprises one or more of a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet.
 18. The machine-readable medium of claim 15, wherein the machine is further caused to: receive a synchronization request to synchronization first content of the child site with one or more of second content of the parent site and third content of the one or more child sites; and synchronize first content of the child site with the one or more of the second content of the parent site and the third content of the one or more child sites.
 19. The machine-readable medium of claim 15, wherein the machine is further caused to: authenticate the first generation request prior to processing the request; and process the request prior to generating the site template.
 20. The machine-readable medium of claim 15, wherein the machine is further caused to: receive a second generation request for generating the child site based on the site template; and receive a mapping request for mapping the child site to the one or more of the parent site and the one or more child sites within the site network. 